Back to Table of Contents Back to Appendix 2
This appendix provides some suggestions on how to plan out the forwarding list to be used by MailDoor, both to support future growth and to better organize your e-mail addresses.
Overall strategy
It is important to plan your forwarding list in a straightforward, organized fashion, both to support future growth and to help you better keep track of your e-mail addresses on a domain-by-domain basis. The goals of your plan should be to develop a logical, consistent structure for your list and to avoid future conflicts which result in the need to "relocate" AIMS users who are using account names which later need to be managed by MailDoor. This section recommends one such plan; there are certainly others that are equally valid.
Functional accounts
The Getting Started section recommends dividing your AIMS accounts into MailDoor and non-MailDoor accounts. When doing so, you should consider making all functional accounts (that is, accounts which are addressed based on function, rather than user name) MailDoor accounts. If you have a functional address within one domain, it is highly likely you will need that functional address for some other domain in the future. Setting up MailDoor to perform the forwarding usually associated with functional addresses will eliminate the chance of any future conflict between domains wishing to use the same functional address. Even if you never have such a conflict, setting up all functional addresses in MailDoor helps you to better keep track of those addresses.
User accounts
The principal reason to set up a non-MailDoor account is to allow an end user to log in to read mail through that account. Since any non-MailDoor account could potentially cause a future conflict, you should consider setting up your non-MailDoor (end user) accounts with names that are unlikely to be needed in the future.
For example, suppose a user within a particular domain requests the e-mail address "John". Instead of creating a non-MailDoor account called "John", create one called, for instance, "mail-John". Have John log in to the "mail-John" account to read his mail. Additionally create a MailDoor account called "John" and configure MailDoor to forward mail from address "John" (within the specific domain for which the account actually exists) to "mail-John". If a user within a second domain then wishes to use the e-mail address "John" as well, you can then create a non-MailDoor account such as "mail-John2", and use MailDoor to forward mail from account "John" within that second domain to "mail-John2".